home *** CD-ROM | disk | FTP | other *** search
- Path: locutus.rchland.ibm.com!usenet
- From: pstaite@vnet.ibm.com
- Newsgroups: comp.lang.c++
- Subject: Re: How can I access more than 64Kb of RAM?
- Date: 15 Jan 1996 15:40:39 GMT
- Organization: IBM OS/2 Device Driver Development Rochester, MN
- Message-ID: <4ddshn$188e@locutus.rchland.ibm.com>
- References: <4d9010$r6v@mother.usf.edu>
- Reply-To: pstaite@vnet.ibm.com
- NNTP-Posting-Host: warpone.rchland.ibm.com
- X-Newsreader: IBM NewsReader/2 v1.2
-
- In <4d9010$r6v@mother.usf.edu>, Christopher Caranna <ccaranna@soleil.acomp.usf.edu> writes:
- > I own a computer with 32Mb of RAM. Unfortunately, I have no idea how
- >to access more than 64Kb (one segment) of it. I would greatly appreciate
- >it if someone would recommend some books that would help explain how to
- >get around this. The technical manuals included with Borland C++ are not
- >clear on this problem.
-
- First choice: get OS/2 Warp and VisualAge C++. ;-) You get a _flat_
- memory model (out to 512 MB) with demand-paged virtual memory, true
- pre-emptive multitasking and multithreading etc. Programming without
- limits (as compared to DOS...). <end commercial>
-
- Second choice, check out the "huge" keyword/extension used by Borland.
- This allows you to point to big buffers (greater than 64K) as in:
-
- char huge *pBigBuf;
-
- And you'll need to allocate space with halloc(). Of course, you'll
- still be limited to 640K DOS memory unless you program using one of the
- DOS extenders to map EMS/XMS memory...
-
- Of course, the Unix types reading this are laughing saying "what's the
- big deal..."
-
-
- Phil Staite, team OS/2
- internet: pstaite@vnet.ibm.com internal: pstaite@rchland
-
-